Remove legacy interaction formats and state identity - #36

packages/tugboat/lib/src/controller.dart:3488

• Completed pointer-linked scrolls are held only in _scrollInteractions, not _activeCompletedGestureCaptures. Clearing this map on session replacement/end or lifecycle deactivation therefore drops the canonical scroll interaction entirely while its capture is pending, contrary to the completed-gesture preservation requirement. Finalize these transactions with the appropriate cancellation reason before clearing the scroll state.

  void _clearScrollCompletionState() {
    _scrollTrackers.clear();
    _scrollInteractions.clear();
    _pendingScrollCompletions.clear();

packages/tugboat/lib/src/viewport_semantic_session.dart:366

• If the current inventory cannot build a semantic map (for example, semantics are temporarily unavailable or the payload exceeds the limit), maybeEmit leaves the previous _latestMap intact and the tap is resolved against stale controls. Clear the cached map before attempting this current-inventory rebuild so failure resolves as unavailable instead of matching the prior screen.

    if (inventory != null) {
      maybeEmit(inventory, resolver: resolver);
    }

docs/README.md:32

• The release metadata now declares session wire schema 10, but this compatibility summary still advertises schema 9. Update it so integrators do not configure readers for the obsolete writer version.

- session JSON schema: `9`;

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

packages/tugboat/lib/src/viewport_semantic_session.dart:160

• This event-level dedupe returns before _recordScrollSemanticSlice. Because every scroll_start now replaces the gesture accumulator, repeating the same semantic slices in a later gesture leaves the new accumulator empty and suppresses its scroll_semantic_snapshot. Record each scroll slice before applying dedupe only to viewport_semantic_map publication.

    final dedupeKey =
        '${map.routeKey}|${map.mapHash}|${map.scrollContext?.dedupeKey ?? ''}';
    if (!_emittedSemanticMaps.add(dedupeKey)) return;

packages/tugboat/test/replay/replay_overlay_nested_navigation_matrix_test.dart:123

• This helper now searches the entire session and returns the first matching route. The test closes /root twice (dialog, then sheet), so the second lookup can return the earlier dialog-pop event and pass even if the sheet pop emitted nothing. Restore an event-index baseline/cursor and search only events produced after the current action.

packages/tugboat/lib/src/viewport_semantic_session.dart:126

• The reset is reached only after the controller has successfully built a non-null scene inventory. _maybeEmitSceneInventory returns before calling this method when buildSceneInventory returns null (controller.dart:3911-3916), so an unavailable inventory at scroll_start leaves the previous gesture's accumulator alive and a later update can stitch slices across two gestures. Reset from recordScrollStart before inventory construction (for example through a dedicated session API); the new unavailable-path test currently passes a stale non-null inventory and does not cover this case.

    if (scrollContext?.trigger == 'scroll_start') {
      _beginScrollSemanticGesture(
        routeKey: inventory.routeKey,
        scroll: scrollContext!,
      );

packages/tugboat/test/viewport_semantic_map_test.dart:210

• This assertion only proves that a tap interaction was emitted; it still passes if tap resolution continues using the stale top-button semantic map and never rebuilds after the same-route widget change. Assert that a second semantic-map event is emitted and that its nodes link the interaction's new target fingerprint so this test actually guards the advertised rebuild behavior.
  packages/tugboat/test/replay/replay_navigation_interaction_matrix_test.dart:10
• The replacement leaves only a direct-controller harness case and removes the real Navigator coverage for named push, replacement, pop, and pushNamedAndRemoveUntil. The overlay suite still exercises widget-backed push/pop, but no widget-backed test now covers replacement or stack cleanup, so regressions in observer callback ordering for those operations would pass despite this PR changing route ownership and causal interaction publication. Retain focused real-widget tests for at least replacement and remove-until.
  packages/tugboat/CHANGELOG.md:11
• These breaking removals are placed under Unreleased, while the package is being bumped to 0.8.0 and a separate 0.8.0 section follows. Published 0.8.0 release notes would therefore imply that the removed publication modes, aliases, and constructors are not part of 0.8.0. Merge this breaking-changes subsection into the 0.8.0 entry.

## Unreleased

### Breaking changes

- The SDK now publishes only schema-v2 canonical `interaction` gesture events.

docs/design/capture-and-fingerprint.md:205

• This says state anchors and signatures remain as internal legacy model data, but this PR deletes TugboatStateAnchor and its resolver/model implementation entirely. Update the design document to describe full removal rather than internal retention.

Version 0.8.0 does not write state identity. State anchors and signatures remain
internal legacy model data only. New event, inventory, semantic-map, diagnostic,
debug, and provenance JSON omit them. Use route evidence, target anchors, and
frame hashes for raw replay facts.